<example id="realtime_reading">
<title>Read realtime positioning from Garmin USB, write to Keyhole Markup</title>
<para>
- <userinput>gpsbabel -T -i garmin -f usb: -o kml -F xxx.kml</userinput>
+ <userinput>gpsbabel -T -i garmin -f usb: -o kml -F example.kml</userinput>
</para>
- <para>Will read the USB-connected Garmin and rewrite 'xxx.kml' atomically,
+ <para>Will read the USB-connected Garmin and rewrite 'example.kml' atomically,
suitable for a self-refreshing network link in Google Earth.
</para>
</example>
<example id="realtime_reading_wintec">
<title>Read realtime positioning from Wintec WBT-201 via Bluetooth on Mac, write to Keyhole Markup</title>
<para>
- <userinput>gpsbabel -T -i nmea -f /dev/cu.G-Rays2-SPPslave-1 -o kml -F xxx.kml</userinput>
+ <userinput>gpsbabel -T -i nmea -f /dev/cu.G-Rays2-SPPslave-1 -o kml -F example.kml</userinput>
</para>
<para>Will read the Wintec WBT-201 via Bluetooth, using the name that
- the Mac assigned it, and rewrite 'xxx.kml' atomically,
+ the Mac assigned it, and rewrite 'example.kml' atomically,
suitable for a self-refreshing network link in Google Earth.
</para>
</example>
<para>
<option>-V</option>Print version number. </para>
</sect1>
-</chapter>
\ No newline at end of file
+</chapter>
This option lets you configure how many digits GPSBabel uses for numbering generated route point names.
</para>
<para>
-When GPSBabel creates route points during the transformation process these points are sequentially numbered and named "RPTxxx" where xxx represent the number. By default GPSBabel uses 3 digits for these numbers. Rationale: This way a large number of route points can be uniquely named while the generated names are limited to 6 characters. This limitation is imposed by specific GPS-devices.
+When GPSBabel creates route points during the transformation process these points are sequentially numbered and named "RPTnnn" where nnn represent the number. By default GPSBabel uses 3 digits for these numbers. Rationale: This way a large number of route points can be uniquely named while the generated names are limited to 6 characters. This limitation is imposed by specific GPS-devices.
</para>
<para>
Using this option GPSBabel can be configured to use less or more digits for the generated names. This option is best used in conjunction with the rptname option.
With this option you can decide to let GPSBabel name generated route points according to their source track name.\r
</para>\r
<para>\r
-GPSBabel creates route points during the transformation process named "RPTxxx" where xxx is a numeric part.</para>\r
+GPSBabel creates route points during the transformation process named "RPTnnn" where nnn is a numeric part.</para>\r
<para>\r
Using this option GPSBabel can be configured to replace the "RPT" part of the generated names by the name of the source track during the transformation process. This is especially usefull if several differently named tracks are contained in the source file which should each be transformed into routes.\r
</para>\r
Some early systems also supported entities called event marker icons.
Event icon markers are represented by symbol, latitude and longitude data only.
By default, event marker icons are converted by GPSBabel to waypoints on read with their name being generated
-in the format "Event Marker XXX"
-where XXX is replaced by the squence number of the Event Marker ICON found in the input data.
+in the format "Event Marker NNN"
+where NNN is replaced by the squence number of the Event Marker ICON found in the input data.
You have the option to ignore Event Icon Markers
effectively removing them from the output data using the input option <emphasis>ignoreicons</emphasis>.
On output, you can use the write option <emphasis>writeasicons</emphasis> to create event marker icons
This option lets you configure how many digits GPSBabel uses for numbering generated route point names.\r
</para>\r
<para>\r
-When GPSBabel creates route points during the transformation process these points are sequentially numbered and named "RPTxxx" where xxx represent the number. By default GPSBabel uses 3 digits for these numbers. Rationale: This way a large number of route points can be uniquely named while the generated names are limited to 6 characters. This limitation is imposed by specific GPS devices.\r
+When GPSBabel creates route points during the transformation process these points are sequentially numbered and named "RPTnnn" where nnn represent the number. By default GPSBabel uses 3 digits for these numbers. Rationale: This way a large number of route points can be uniquely named while the generated names are limited to 6 characters. This limitation is imposed by specific GPS devices.\r
</para>\r
<para>\r
Using this option GPSBabel can be configured to use less or more digits for the generated names. This option is best used in conjunction with the rptname option.\r
With this option you can decide to let GPSBabel name generated route points according to their source track name.\r
</para>\r
<para>\r
-GPSBabel creates route points during the transformation process named "RPTxxx" where xxx is a numeric part.</para>\r
+GPSBabel creates route points during the transformation process named "RPTnnn" where nnn is a numeric part.</para>\r
<para>\r
Using this option GPSBabel can be configured to replace the "RPT" part of the generated names by the name of the source track during the transformation process. This is especially useful if several differently named tracks are contained in the source file which should each be transformed into routes.\r
</para>\r
+++ /dev/null
-<para>
-DeLorme XMapHandHeld Street Atlas USA is another of the
-billion <link linkend="fmt_csv"> CSV variants</link>.
-This is the format used by XmapHH SA USA on (at least) PocketPC O/S.
-</para>
-<para>
-This XMap is not the same as the simpler
-<link linkend="fmt_xmap">XMap</link> format, which is used with Topo USA 4.0
-and XMapHH for Palm.
-</para>
-<para>
-DeLorme XMap Handheld .WPT for PocketPC is a bit of a kludge. This
-chapter covers XMap Handheld Street Atlas USA edition.
-</para>
-<para>
-XMap on the PocketPC stores its waypoints in individual .wpt files.
-For example, waypoints generated by XMap on the PocketPC are stored
-by default in the "My Documents" folder using the sequential names
-"XMap1.wpt", "XMap2.wpt", ad nauseam. Needless to say, this is not very
-efficient.
-</para>
-<para>
-As writing multiple waypoint files is outside of the scope of GPSBabel,
-GPSBabel chooses to write one big file, one waypoint per line.
-Extracting lines from this file is left as an exercise for the end user.
-A simple Perl script to handle this conversion is included at the end
-of this chapter.
-</para>
-<para>
-It should also be noted that <emphasis>reading</emphasis> multiple files
-is indeed possible, but if you have more than a few points, it can be a task.
-For example:
-</para>
-<para><userinput>gpsbabel -i xmapwpt -f Xmap1.wpt -f Xmap2.wpt -o mapsend -F mapsend.wpt</userinput></para>
-<para>
-will read the two Xmap .wpt files and write one mapsend file. This
-is fine for a small handful of points, but could be quite cumbersome
-for folks like me who have 100+ waypoints loaded into XMap. For *nix
-folks, something as simple as:
-</para>
-<para><userinput>cat *.wpt > /tmp/foo.wpt</userinput>
-<userinput>gpsbabel -i xmapwpt -f foo.wpt -o mapsend -F mapsend.wpt </userinput></para>
-<para>
-will do the trick just fine.
-</para>
-<programlisting>
-#!/full/path/to/perl
-$INPUTFILE = @ARGV[0];
-$TARGETDIR = @ARGV[1];
-$FILENAME = @ARGV[2];
-
-if (! $FILENAME) {
- print "Usage: xmap_split.pl " .
- "INPUT_FILE OUTPUT_DIRECTORY FILENAME_BASE\n";
- print " (i.e. xmapl_split.pl points.wpt /tmp/points GPSB)\n";
- print " (created GPSB0001-GPSBXXXX " .
- " in /tmp/points/ from points.wpt)\n";
- exit;
-}
-
-open (INFILE, $INPUTFILE) || die "Cannot open $INPUTFILE for read!\n";
-
-while (<INFILE>) {
- $lc++;
- $filename = sprintf("%s/Gpsb%04d.wpt", $TARGETDIR, $lc);
-
- open (OUTFILE, ">$filename") ||
- die "Cannot open $filename for write!\n";
-
- print OUTFILE $_;
-
- close(OUTFILE);
-}
-
-exit;
-
-</programlisting>
-
-<para>Contributed to GPSBabel by Alex Mottram.</para>
-
projects / gpsbabel.git / commitdiff